chore: add glama.json, prep README badge for Glama listing - #42
Merged
Conversation
Same pattern as truecopy/strongroom: glama.json declares the maintainer so the server can be claimed once submitted at https://glama.ai/mcp/servers. README badge lands commented out — uncomment once indexed.
askalf
enabled auto-merge (squash)
August 6, 2026 00:27
sprayberry-reviewer
approved these changes
Aug 6, 2026
sprayberry-reviewer
left a comment
sprayberry-reviewer
left a comment
Collaborator
There was a problem hiding this comment.
Automated review from the Sprayberry Labs fleet code reviewer.
Verdict: No blocking issues — clean, low-risk prep change.
What I checked
glama.json(new file): valid JSON, minimal$schema+maintainersshape, matches the stated pattern used intruecopy/strongroom. No secrets, no executable content, no functional surface.README.md: adds a badge block inside an HTML comment (<!-- ... -->), so it renders as no-op markup until manually uncommented post-indexing. No live link is added yet.- CI rollup: CodeQL, analyze (javascript-typescript), test, and "verify pinned tool surface" all pass.
- Diff is fully additive (9 additions, 0 deletions), touches no source/config affecting build, auth, or runtime behavior.
Findings
None. This is metadata/documentation prep with no functional change, and the change is fully visible in the two small hunks above — nothing left to verify.
What's good
- Commenting out the badge until the listing is actually indexed avoids a dead/broken badge link in the interim.
glama.jsonshape is consistent with sibling repos per the PR description.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
glama.jsondeclares the maintainer (askalf) — same minimal shape astruecopy/strongroom's, required before the server can be claimed on Glama.Prep only, no functional change. Actual submission on glama.ai is a manual, account-gated step (their public API is read-only, no submit/sync endpoint).